Sharing media among remote access clients in a universal plug and play environment

ABSTRACT

In general, in one aspect, the disclosure describes a Universal Plug and Play (UPnP) Remote Access Server (RAS) to provide a communication channel between UPnP Remote Access Clients (RACs) connected thereto. The UPnP RAS maintains local discovery information for UPnP devices connected to a local network and remote discovery information for remote UPnP devices communicating therewith. The UPnP RAS provides the remote UPnP devices communicating therewith with the local discovery information and the remote discovery information. The remote discovery information is utilized by a first remote UPnP device to discover a second UPnP device and vice versa. After discovery, a first remote UPnP device can communicate with a second UPnP device and vice versa.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/269,758, filed Sep. 19, 2016, which is a continuation of U.S. patentapplication Ser. No. 13/885,204, filed May 14, 2013, which is the UnitedStates National Phase Application Under 35 U.S.C. § 371 of InternationalApplication No. PCT/CN2010/079695, filed Dec. 13, 2010, each of which ishereby incorporated by reference herein in its entirety.

BACKGROUND

Universal Plug and Play (UPnP) technology was initially deployed inlocal area networks. UPnP technology enables UPnP devices to be added toa UPnP local network without the need for drivers or configuring of thedevice and/or network. The device and the network can discover eachother, the device can be assigned an ID (IP address) by the network, thedevice and network can exchange information, and then the device andother devices attached to the network can communicate using theassociated IP addresses. UPnP has been expanded beyond the physicalboundaries of local area networks to enable remote devices to haveremote access to the network.

FIG. 1A illustrates an example connection of a remote device (e.g.,portable computer, wireless device) 110 to a device 120 connects to alocal network (e.g., home network) 130 utilizing UPnP technology. Theremote device 110 connects to a router and or gateway 150 of the localnetwork 130 via the Internet 140 and then once connected to the localnetwork 130 connects to the local device 120. Before the UPnP device 110can be used to remotely access the UPnP network 130 and the UPnPdevice(s) 120 connected thereto, a Remote Access Server (RAS) has to beestablished within the local network 130 (e.g., in the router/gateway150) and the device 110 needs to be established as a Remote AccessClient (RAC).

FIG. 1B illustrates a simplified block diagram of example devices 110,150 configured as a RAC and a RAS respectively and a securecommunications link 160 therebetween. The remote device 110 can includea processor 111, a computer readable storage medium 112, and acommunication interface 119. The processor 111, the computer readablestorage medium 112, and the communication interface 119 are not limitedto any particular type, configuration, or number as these may vary basedon, among other things, the device 110 and the system the device 110 isoperating in. The computer readable storage medium 112 can be in wholeor part external to the device 110.

The computer readable storage medium 112 can store processor-executableinstructions, which, when executed by the processor 111 cause theprocessor 111 to perform certain functions and the device 110 to operatein a certain fashion. The processor-executable instructions can includeoperational instructions 113 and RAC instructions 114. The operationalinstructions 113 can be used to operate the device 110 and the servicesperformed by the device 110 or the applications running on the device110. The operational instructions 113 are illustrated as a single blockbut are in no way limited to a single set of instructions. Rather, theoperational instructions 113 can be a plurality of instructions setsnecessary to operate the device 110 and the applications runningthereon.

The RAC instructions 114 can include Remote Access Transport Agent(RATA) instructions 115 and Remote Access Discovery Agent (RADA)instructions 116. The RATA instructions 115 can provide the securecommunications between the device 110 and the router 150 via thecommunications interface 119. The RADA instructions 116 can maintaindiscovery information for the device 110 and other local devicesconnected thereto (RAC discovery information), can synchronize the localRAC discovery information to the router/gateway (configured as a RAS)150 once communications have been established therebetween, can receivethe discovery information for devices local to the RAS 150 (RASdiscovery information) and can maintain the RAS discovery information asremote discovery information.

The router/gateway 150 can include a processor 151, a computer readablestorage medium 152, and a communication interface 159. The processor151, the computer readable storage medium 152, and the communicationinterface 159 are not limited to any particular type, configuration, ornumber as these may vary based on, among other things, therouter/gateway 150 and the system the router/gateway 150 is operatingin. The computer readable storage medium 152 can storeprocessor-executable instructions, which, when executed by the processor151 cause the processor 151 to perform certain functions. Theprocessor-executable instructions can include operational instructions153 and RAS instructions 154. The operational instructions 153 can beused to operate the router/gateway 150 and the services performedthereby (e.g., routing).

The RAS instructions 154 can include RATA instructions 155, RADAinstruction 156, RADA configuration instructions 157, and inboundconnection configuration instructions 158. The RATA instructions 155 canprovide the secure communications between the router/gateway 150 and thedevice 110 via the communications interface 159. The RADA instructions156 can maintain discovery information for devices 120 connected to thelocal network 130 (RAS discovery information), can receive discoveryinformation for remote devices (configured as a RAC) 110 oncecommunications have been established therebetween (RAC discoveryinformation), can maintain the RAC discovery information as remotediscovery information, and can synchronize the local RAS discoveryinformation to the RAC 110 once communications have been establishedtherebetween.

The RADA configuration instructions 157 can enable the operator of thenetwork 130 to limit the local discovery information that therouter/gateway 150 provides to RACs. For example, if a secure server wasincluded on the network 130 the instructions 157 could restrict thediscovery information associated therewith from being synchronized withremote devices 110. The inbound connection configuration instructions158 can verify that the RAS can be reached by the Internet (e.g., publicIP address) and configure settings to allow the RACs to establish a RATAconnection thereto.

Once the RAS 150 and the RAC 110 are configured, the RAC 110 caninitiate contact with the RAS 150 and a Remote Access Transport (RAT)channel 160 can be established therebetween. Once the RAT channel 160 isestablished, the RADA instructions 116, 156 can synchronize UPnPdiscovery information between the RAC 110 and RAS 150. After discoveryinformation is synched, the remote device 110 can communicate with thelocal devices 120 and vice versa in a similar fashion to the localdevices 120 communicating therebetween subject to parameters associatedwith external networks and access points between networks.

FIG. 2 illustrates an example connection between a plurality of remotedevices (e.g., portable computer, wireless device) 210, 220 and a localnetwork (e.g., home network) 230 utilizing UPnP technology. The remotedevices 210, 220 can be configured as RACs (as illustrated) or can beconnected to a network 214, 224 that includes devices configured asRACs. A router or gateway 232 of the local network 230 can be configuredas a RAS (as illustrated) or the RAS can be a separate device on thenetwork 230. The remote devices 210, 220 can include media servers 212,222 or the devices 210, 220 can be connected to the media servers 212,222 via the respective network 214, 224 (as illustrated). RAT channels240, 250 can be established between the corresponding RAC 210, 220 andthe RAS 232 of the local network 230 via the Internet 260.

A user of the RAC 210 (or other devices connected to the network 214such as a media server 212) can discover the media server 234 and accesscontent thereon, and a user of a device (e.g., media server 234) on thelocal network 230 can discover the media server 212 and access contentthereon via the RAT channel 240. Likewise, a user of the RAC 220 (orother devices connected to the network 224 such as a media server 222)can discover the media server 234 and access content thereon, and a userof a device on the local network 230 can discover the media server 222and access content thereon via the RAT channel 250.

FIG. 3 illustrates an example of discovery information aggregated foreach of the RACs 210, 220 and the RAS 232 of FIG. 2. The discoveryinformation for the RAS 232 includes information related to the localnetwork 230 including information for the media server 234, informationfor the remote network 214 including information related to the mediaserver 212 and information for the remote network 224 includinginformation related to the media server 222. The discovery informationfor the RAC 210 includes information related to its local network 214including information for the media server 212 and information for theremote home network 230 including information related to the mediaserver 234. The discovery information for the RAC 220 includesinformation related to its local network 224 including information forthe media server 222 and information for the remote home network 230including information related to the media server 234.

As the RAC 210 does not include information about the network 224 or thedevices connected thereto it can not discover the network 224 or thedevices 220, 222 connected thereto. Likewise, as the RAC 220 does notinclude information about the network 214 or the devices connectedthereto it can not discover the network 214 or the devices 210, 212connected thereto. As such, users of devices 210, 212 on the network 214(user A) can not communicate with the users of devices 220, 222 on thenetwork 224 (user B) or vice versa. That is, there is no RAC to RACcommunications vehicle.

Accordingly, if a user A wanted to share some media (e.g., pictures,videos) from their media server 212 with user B they would have to copythe content to media server 234 and then user B could access the contentfrom the media server 234. The same would be the case if user B wantedto share content with user A. Having to copy content to the media server234 on the local network (home network) 230 is not convenient orefficient and has issues associated therewith. For example, the mediaserver 234 may not have sufficient storage or the users of the network230 may not want the remote users (users A and B) copying data to themedia server 234. Furthermore, the remote users (users A and B) may onlywant to share their content with certain devices and not everyone havingaccess to the media server 234 and requiring the media server 234 toprovide access control for remote content copied thereto would beburdensome.

In order for user A to share content with user B and vice versa withoutthe need to copy the content to the media server 234 that they both haveaccess to, user A (or user B) would need to configure a device withintheir network 214 (or network 224) as a RAS and would need to identifythe RAC 220 (or RAC 210) as an authorized user in order to establish aRAT channel therebetween. The device to be configured as the RAS wouldneed to have a public IP address that could be used to allow access touser B (or user A). Configuring a remote device to be a RAS is notconvenient or efficient and has issues associated therewith. Forexample, the occasions when the remote devices may want to remotelyshare content may be limited and therefore not justify the configurationeffort. Additionally, the remote devices wishing to share contentremotely may not be capable of being assigned a public IP address orbeing reached remotely over the Internet. Furthermore, the remotedevices may not have sufficient storage medium capacity or processorcapability to store or run the RAS instructions 154. Moreover, thenetwork that the remote device is connected to may not be designed toallow external discovery of network devices (e.g., work network withfirewalls).

SUMMARY

A universal plug and play (UPnP) remote access server (RAS) to enablecommunications between UPnP remote access clients (RACs) connectedthereto is disclosed. The UPnP RAS includes a processor and computerreadable storage medium to store processor-executable instructions. Theprocessor-executable instructions, when executed by the processor, causethe processor to: establish a first remote access transport (RAT)channel with a first remote UPnP device that initiates communicationtherewith; receive discovery information for the first remote UPnPdevice; add the discovery information for the first remote UPnP deviceto a first remote branch of discovery information; establish a secondRAT channel with a second remote UPnP device that initiatescommunication therewith; and provide the first remote branch ofdiscovery information to the second remote UPnP device. The secondremote UPnP device can discover the first remote UPnP device based onthe first remote branch of discovery information provided thereto andcan access the first remote UPnP device using the second RAT channelfrom the second remote UPnP device and the first RAT channel to thefirst remote UPnP device.

A UPnP RAS to enable communications between UPnP RACs connected theretois disclosed. The UPnP RAS includes a first interface to communicatewith a local network and UPnP devices connected thereto and a secondinterface to communicate externally via the Internet. A remote accesstransport agent (RATA) is configured to establish RAT channels withremote UPnP devices that initiate communication therewith. A remoteaccess discovery agent (RADA) is configured to: detect local UPnPdevices connected to the local network; receive discovery informationfor the local UPnP devices; add the discovery information for the localUPnP devices to a local branch of discovery information; receivediscovery information for a first remote UPnP device to communicatetherewith; add the discovery information for the first remote UPnPdevice to a first remote branch of discovery information; provide thelocal branch of discovery information to the first remote UPnP device;receive discovery information for a second remote UPnP device tocommunicate therewith; add the discovery information for the secondremote UPnP device to a second remote branch of discovery information;provide the local branch of discovery information to the second remoteUPnP device; provide the first remote branch of discovery information tothe second remote UPnP device; and provide the second remote branch ofdiscovery information to the first remote UPnP device. The second remoteUPnP device can utilize the first branch of discovery information todiscover the first remote UPnP device and can access the first remoteUPnP device using the RAT channels between the second remote UPnP deviceand the UPnP RAS and the UPnP RAS and the first remote UPnP device. Thefirst remote UPnP device can utilize the second branch of discoveryinformation to discover the second remote UPnP device and can access thesecond remote UPnP device using the RAT channels between the firstremote UPnP device and the UPnP RAS and the UPnP RAS and the secondremote UPnP device.

A processor implemented method performed in a UPnP RAS to provide acommunication channel between UPnP RACs connected thereto is disclosed.The processor implemented method includes the processor: maintaininglocal discovery information for UPnP devices connected to a localnetwork; maintaining remote discovery information for remote UPnPdevices communicating therewith; and providing the remote UPnP devicescommunicating therewith with the local discovery information and theremote discovery information. The remote discovery information isutilized by a first remote UPnP device to discover a second UPnP device.

BRIEF DESCRIPTIONS OF THE DRAWINGS

The features and advantages of the various embodiments will becomeapparent from the following detailed description in which:

FIG. 1A illustrates an example connection of a remote device to a localdevice utilizing universal plug and play (UPnP) technology, according tothe prior art.

FIG. 1B illustrates a simplified block diagram of example devicesconfigured as a remote access client (RAC) and a remote access server(RAS) respectively and a secure communications link therebetween,according to the prior art.

FIG. 2 illustrates an example connection between a plurality of remotedevices and a local network utilizing UPnP technology, according to theprior art.

FIG. 3 illustrates an example of discovery information aggregated foreach of the RACs and the RAS of FIG. 2, according to the prior art.

FIG. 4 illustrates a flow chart of example high level actions to enableremote devices to discover one another by utilizing the RAS, accordingto one embodiment.

FIG. 5 illustrates an example of aggregated discovery information forthe RACs and the RAS of FIG. 2 utilizing the example flow chart of FIG.4, according to one embodiment.

FIG. 6 illustrates a detailed process flow diagram of example actions tobe taken by each of the associated devices of FIG. 2 to enable the RACsto discover one another by utilizing the RAS, according to oneembodiment.

DETAILED DESCRIPTION

Referring to components illustrated in FIG. 2, the current invention canprovide a Remote Access Server (RAS) 232 that enables the remote devicesconfigured as Remote Access Clients (RACs) 210, 220 to communicate withone another (e.g., share content) without the need to copy their contentto the media server 234 on the local network 230 or configure one of theremote devices 210, 220 as a RAS. The RAS 232 of the current inventioncan enable the RAC 210 (or RAC 220) to discover the other RAC 220 (orRAC 210) connected to the RAS 232. If the RACs 210, 220 can discovereach other they can utilize the existing Remote Access Transport (RAT)channels 240, 250 between the RAS and the RACs 210, 220 respectively tocommunicate (exchange information) with one another.

Referring to components illustrated in FIG. 1B, the Remote AccessDiscovery Agent (RADA) instructions 116 can maintain discoveryinformation for the RAC and devices connected to the RAC (localdiscovery information) and discovery information provided by the RAS fordevices connected to the RAS (remote discovery information). The RADAinstructions 156 can maintain discovery information for devicesconnected to the RAS (local discovery information) and discoveryinformation provided by the RAC for the RAC and the devices connectedthereto (remote discovery information). As illustrated in FIG. 3, ifmultiple RACs are in communication with the RAS, the RADA instructions156 can maintain multiple remote discovery branches (e.g., a branch foreach RAC).

The RADA instructions 116 (or 156) can provide their local discoveryinformation to the RAS (or RAC) when communications between the RAC andRAS are first established. In addition, RADA instructions 116 (or 156)can provide their local discovery information to the RAS (or RAC) whenthe local discovery information changes (e.g., local device added, localdevice removed). Based on the local and remote discovery informationmaintained for a RAC, the RAC can discover and access any devicesconnected to itself or the RAS. Based on the local and remote discoveryinformation maintained for a RAS, devices connected to the RAS candiscover and access any other devices connected to the RAS, or any RACor any devices connected to any RAC in communication with the RAS.

According to one embodiment, the RADA instructions 156 can be modifiedto synchronize both its local discovery information and its remotediscovery information with any RACs connected thereto. The RADAinstructions 156 can synchronize the local and remote discoveryinformation when communications is first established with a RAC and whenchanges are made to the local discovery information or the remotediscovery information. The changes to the remote discovery informationcan include the addition of a new remote discovery information whencommunications with a new RAC is established or the update of a remotebranch based on updated discovery information received from a currentRAC. The synchronization of the remote discovery information by the RADAinstructions 156 enables the RADA instructions 116 to receive andmaintain remote discovery information for the RAS as well as other RACsin communication with the RAS.

The RADA configuration instructions 157 can be modified to enable theoperator of the network or a user of a RAC to filter the remotediscovery information that the RADA instructions 156 provide to the RADAinstructions 116. For example, a user of a remote device containingproprietary data may want the number of remote users having accessthereto blocked or limited. The RADA instructions 116 may need to bemodified to maintain separate branches of remote discovery information(e.g., one branch for each remote connection).

With a RAC having the discovery information for other remote RACsmaintained therein, the RAC can use the discovery information todiscover and access the other remote RACs or devices connected thereto.Communications (e.g., file sharing) between remote RACs (or devicesconnected to the remote RACs) can be accomplished without the need tocopy content to a device (e.g., media server) connected to the RAS via alocal network.

FIG. 4 illustrates a flow chart of example high level actions that canbe taken to enable first and second remote devices (RACs) to discoverone another by utilizing a RAS. The flow chart starts under theassumption that the RAS and the RACs have been configured and that theRACs are authorized to access the RAS. Initially, the first RAC (e.g.,RAC 210 in FIG. 2) can connect to the RAS (e.g., RAS 232 in FIG. 2) 400.The first RAC and the RAS can then synchronize their discoveryinformation 410. The first RAC can provide its local discoveryinformation (discovery information about itself and what can beconnected thereto) to the RAS and the RAS can add this discoveryinformation as a remote branch. The RAS can provide all its discoveryinformation to the first RAC. As the RAS only has local discoveryinformation at this point (excluding the remote discovery informationjust added for the first RAC that is the same as the local discoveryinformation for the first RAC) that is all that is provided to the firstRAC. The first RAC can add this discovery information as a remotebranch. The first RAC can propagate the remote branch discoveryinformation (provided by the RAS) to other devices connected thereto(e.g., the media server 212 or other devices connected to the network214 in FIG. 2).

The second RAC (e.g., RAC 220 in FIG. 2) can connect to the RAS 420. Thesecond RAC and the RAS can then synchronize their discovery information430. The second RAC can provide its local discovery information to theRAS and the RAS can add this discovery information as a remote branch.The remote branch for the second RAC can be separate from the remotebranch for the first RAC. The RAS can provide all its discoveryinformation to the second RAC. The discovery information can includelocal discovery information and remote discovery information for thefirst RAC (the remote discovery information just added for the secondRAC that is the same as the local discovery information for the secondRAC can be excluded). The second RAC can add the local RAS discoveryinformation and the remote first RAC discovery information as a remotebranch (or remote branches). The remote branch for the RAS can beseparate from the remote branch for the first RAC. The second RAC canpropagate the discovery information from the remote branches (providedby the RAS) to other devices connected thereto (e.g., the media server222 or other devices connected to the network 224 in FIG. 2).

The addition of the discovery information for the second RAC to theremote discovery information for the RAS is a change to the discoveryinformation of the RAS that can initiate the RAS synchronizing itsdiscovery information. The synchronizing of the discovery informationcan be limited to the first RAC (since the changes were initiated by thesecond RAC and the second RAC remote branch of the RAS is the same asthe local branch for the second RAC). The RAS can synchronize all of itsdiscovery information, just the remote discovery information, or justthe newly added remote discovery information. The first RAC can add thenew discovery information to a remote branch (new remote branch separatefrom remote branch capturing RAS). The first RAC can propagate the newremote branch discovery information (provided by the RAS) to otherdevices connected thereto (e.g., the media server 212 or other devicesconnected to the network 214 in FIG. 2).

FIG. 5 illustrates an example of aggregated discovery information forthe RACs 210, 220 and the RAS 232 of FIG. 2 utilizing the example flowchart of FIG. 4. The discovery information for the RAS 232 is like thatillustrated in FIG. 3 (local network 230 information, remote network 214information, and remote network 224 information). The discoveryinformation for the RAC 210 includes its local network 214 informationand the remote home network 230 information as previously illustrated inFIG. 3, in addition to discovery information for the remote network 224including information related to the media server 222 (provided by theRAS 232). The discovery information for the RAC 220 includes localnetwork 224 information and remote home network 230 information aspreviously illustrated in FIG. 3, in addition to discovery informationfor the remote network 214 including information related to the mediaserver 212 (provided by the RAS 232).

FIG. 6 illustrates a detailed process flow diagram of example actions tobe taken by each of the associated devices of FIG. 2 that will enablethe remote devices (RACs) 210, 220 to discover one another by utilizingthe RAS 232. The diagram is broken down into each of the respectivenetworks 214, 224, 230 and their associated devices (media server 212,RAC 210, media server 222, RAC 220, media server 234 and RAS 232).

Initially each of the media servers 212, 222, 234 connect to therespective networks 214, 224, 230 (600, 602, 604). The media servers212, 222, 234 can send the networks 214, 224, 230 messages (e.g.,ssdp:alive messages) to indicate they desire to connect thereto (606,608, 610). The RACs 210, 220 and RAS 232 can receive these messages anddiscover the media servers 212, 222, 234 and then add the media servers212, 222, 234 to their local branch of discovery information (612, 614,616).

The RAC 210 can connect to the RAS 232 (618) and a secure RAT channelcan be established between the RAC 210 and the RAS 232 (620). The RAS232 can synchronize the device information from its local branch (e.g.,media server 234) to RAC 210 (622). The RAC 210 can add the media server234 to a remote branch of discovery information (624). The remote branchcan be associated with the network 230. The RAC 210 can synchronize thedevice information from its local branch (e.g., media server 212) to theRAS 232 (626). The RAS 232 can add the media server 212 to a remotebranch of discovery information (628). The remote branch can beassociated with the network 214.

The RAC 220 can connect to the RAS 232 (630) and a secure RAT channelcan be established between the RAC 220 and the RAS 232 (632). The RAS232 can synchronize the device information from its local branch (e.g.,media server 234) and from its remote branch (e.g., media server 212) toRAC 220 (634). The RAC 220 can add the media servers 212, 234 to aremote branch(s) of discovery information (636). The media server 212can be added to a remote branch associated with network 214 and themedia server 234 can be added to a remote branch for the network 230.The synchronization of media servers (634) and the adding of the mediaservers to remote branches (636) are illustrated as happening together,but could be preformed separately without departing from the currentscope. That is, the RAS 232 could synchronize its local branch first andthen synchronize its remote branch or vice versa.

The RAC 220 can synchronize the device information from its local branch(e.g., media server 222) to the RAS 232 (638). The RAS 232 can add themedia server 222 to a remote branch of discovery information (640). Theremote branch can be associated with the network 224. The RAS 232 canthen synchronize the device information from its remote branch (e.g.,media server 222) to the RAC 210 (642). The RAC 210 can add the mediaserver 222 to a remote branch of discovery information (644). The mediaserver 222 can be added to a remote branch associated with network 224.

The RACs 210, 220 now include discovery information for other remotenetworks. After the discovery information is propagated to the networks214, 224, the RAC 220 can find and browse the media content of mediaserver 212 (646) and the RAC 210 can find and browse the media contentof media server 222 (648).

The synchronization of both local and remote discovery information by aRAS 232 enables communications between the remote devices (configured asauthorized RACs) 210, 220 to occur while only utilizing a single RAS(avoid unnecessary complex configuration of an additional RAS, onlyrequire one public IP address). The remote devices (RACs) 210, 220 caneasily share their own media content (or content from media servers 212,222) with each other by connecting to the RAS 232. Digital home networkusers can more easily and conveniently share media content with eachother even when the users are all remote from the home network 230.

Although the disclosure has been illustrated by reference to specificembodiments, it will be apparent that the disclosure is not limitedthereto as various changes and modifications may be made thereto withoutdeparting from the scope. Reference to “one embodiment” or “anembodiment” means that a particular feature, structure or characteristicdescribed therein is included in at least one embodiment. Thus, theappearances of the phrase “in one embodiment” or “in an embodiment”appearing in various places throughout the specification are notnecessarily all referring to the same embodiment.

The various embodiments are intended to be protected broadly within thespirit and scope of the appended claims.

1. (canceled)
 2. A system for remote communications between remoteaccess clients connected thereto, the system comprising: a memory; and ahardware processor that, when executing computer-readable instructionsstored in the memory, is configured to: establish a first communicationschannel with a first remote device; in response to establishing thefirst communications channel with the first remote device, exchangediscovery information with the first remote device by receiving a firstportion of discovery information from the first remote device andtransmitting at least a portion of aggregated discovery information tothe first remote device, and add the first portion of discoveryinformation received from the first remote device to the aggregateddiscovery information; establish a second communications channel with asecond remote device; and in response to establishing the secondcommunications channel with the second remote device, transmitting atleast the portion of aggregated discovery information to the secondremote device based on allowance information for accessing the firstremote device.
 3. The system of claim 2, wherein the hardware processoris further configured to determine whether to exchange discoveryinformation for the first remote device and the second remote devicebased on the allowance information for accessing the first remotedevice, wherein the at least the portion of aggregated discoveryinformation is transmitted to the second remote device in response todetermining that the discovery information for the first remote deviceis to be exchanged with the second remote device.
 4. The system of claim3, wherein, in response to determining that the discovery informationfor the first remote device is to be exchanged with the second remotedevice, the hardware processor is further configured to exchangediscovery information with the second remote device by: receiving asecond portion of discovery information from the second remote device;adding the second portion of discovery information to the aggregateddiscovery information; and transmitting the second portion of discoveryinformation to the first remote device.
 5. The system of claim 2,wherein the first remote device discovers the second remote device basedon the second portion of discovery information.
 6. The system of claim2, wherein the hardware processor is further configured to: detect localdevices connected to a local network; receive discovery informationassociated with the local devices; and add the discovery informationassociated with the local devices to the aggregated discoveryinformation.
 7. The system of claim 6, wherein the first remote devicediscovers the local devices based on the aggregated discoveryinformation and accesses one or more of the local devices using thefirst communications channel.
 8. The system of claim 6, wherein thesecond remote device discovers the local devices based on the aggregateddiscovery information and accesses one or more of the local devicesusing the second communications channel.
 9. The system of claim 6,wherein the hardware processor is further configured to: detect changesto the local devices connected to the local network; update thediscovery information for the local devices in a local branch of theaggregated discovery information; and transmit the updated local branchof aggregated discovery information to each of the first remote deviceand the second remote device.
 10. The system of claim 2, wherein thehardware processor is further configured to: receive updated discoveryinformation for the first remote device; update a remote branch of theaggregated discovery information to reflect the updated discoveryinformation for the first remote device; and transmit the updated remotebranch of the aggregated discovery information to the second remotedevice.
 11. The system of claim 2, wherein the hardware processor isfurther configured to: receive updated discovery information for thesecond remote device; update a remote branch of the aggregated discoveryinformation to reflect the updated discovery information for the secondremote device; and transmit the updated remote branch of the aggregateddiscovery information to the first remote device.
 12. A method forremote communications between remote access clients connected thereto,the method comprising: establishing a first communications channel witha first remote device; in response to establishing the firstcommunications channel with the first remote device, exchange discoveryinformation with the first remote device by receiving a first portion ofdiscovery information from the first remote device and transmitting atleast a portion of aggregated discovery information to the first remotedevice, and add the first portion of discovery information received fromthe first remote device to the aggregated discovery information;establish a second communications channel with a second remote device;and in response to establishing the second communications channel withthe second remote device, transmitting at least the portion ofaggregated discovery information to the second remote device based onallowance information for accessing the first remote device.
 13. Themethod of claim 12, further comprising determining whether to exchangediscovery information for the first remote device and the second remotedevice based on the allowance information for accessing the first remotedevice, wherein the at least the portion of aggregated discoveryinformation is transmitted to the second remote device in response todetermining that the discovery information for the first remote deviceis to be exchanged with the second remote device.
 14. The method ofclaim 13, further comprising exchanging discovery information with thesecond remote device in response to determining that the discoveryinformation for the first remote device is to be exchanged with thesecond remote device, the hardware processor is further configured toby: receiving a second portion of discovery information from the secondremote device; adding the second portion of discovery information to theaggregated discovery information; and transmitting the second portion ofdiscovery information to the first remote device.
 15. The method ofclaim 12, wherein the first remote device discovers the second remotedevice based on the second portion of discovery information.
 16. Themethod of claim 12, further comprising: detecting local devicesconnected to a local network; receiving discovery information associatedwith the local devices; and adding the discovery information associatedwith the local devices to the aggregated discovery information.
 17. Themethod of claim 16, wherein the first remote device discovers the localdevices based on the aggregated discovery information and accesses oneor more of the local devices using the first communications channel. 18.The method of claim 16, wherein the second remote device discovers thelocal devices based on the aggregated discovery information and accessesone or more of the local devices using the second communicationschannel.
 19. The method of claim 16, further comprising: detectingchanges to the local devices connected to the local network; updatingthe discovery information for the local devices in a local branch of theaggregated discovery information; and transmitting the updated localbranch of aggregated discovery information to each of the first remotedevice and the second remote device.
 20. The system of claim 12, furthercomprising: receiving updated discovery information for the first remotedevice; updating a remote branch of the aggregated discovery informationto reflect the updated discovery information for the first remotedevice; and transmitting the updated remote branch of the aggregateddiscovery information to the second remote device.
 21. The system ofclaim 12, further comprising: receiving updated discovery informationfor the second remote device; updating a remote branch of the aggregateddiscovery information to reflect the updated discovery information forthe second remote device; and transmitting the updated remote branch ofthe aggregated discovery information to the first remote device.
 22. Amethod for remote communications between remote access clients connectedthereto, the method comprising: maintaining local discovery informationfor local devices connected to a local network; maintaining remotediscovery information for remote devices communicating therewith; and inresponse to connecting with each of the remote devices: determiningwhether to exchange the local discovery information and the remotediscovery information based on a number of remote users allowed toaccess the remote devices; and in response to determining that the localdiscovery information and the remote discovery information are to beexchanged, exchanging the discovery information with the connectedremote device by receiving a portion of discovery information from theconnected remote device, and transmitting the local discoveryinformation and the remote discovery information for the remote devicescommunicating therewith.